Search Results

Standard

Recommended Practice for Pass-Thru Vehicle Programming

2002-02-28

HISTORICAL

J2534_200202

This SAE Recommended Practice provides the framework to allow reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (ECU’s) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers. This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer. The U.S.

Standard

Recommended Practice for Pass-Thru Vehicle Programming

2019-07-29

CURRENT

J2534_201907

This SAE Recommended Practice provides the framework to allow reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (ECU’s) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers. This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer. The U.S.

Standard

TP2.0 Vehicle Diagnostic Protocol

2008-02-01

HISTORICAL

J2819_200802

This Technical Information Report defines the diagnostic communication protocol TP2.0. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP2.0 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an SAE J2534 interface.

Standard

Vehicle OBD II Compliance Test Cases

2015-07-28

HISTORICAL

J1699/3_201507

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/EDiagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics - Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

Standard

Vehicle OBD II Compliance Test Cases

2017-07-21

HISTORICAL

J1699/3_201707

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/E Diagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics – Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

Standard

Vehicle OBD II Compliance Test Cases

2021-04-28

CURRENT

J1699/3_202104

The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534-2 feature “Mixed Format Frames on a CAN Network.”

Standard

Vehicle OBD II Compliance Test Cases

2012-05-11

HISTORICAL

J1699/3_201205

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/E Diagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics – Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

Standard

Vehicle OBD II Compliance Test Cases

2021-05-04

WIP

J1699/3

The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534 2 feature “Mixed Format Frames on a CAN Network.”

Standard

Recommended Practice for Diagnostic Trouble Code Definitions

1999-03-01

HISTORICAL

J2012_199903

This SAE Recommended Practice is applicable to all light-duty and medium-duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair databases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

Standard

Diagnostic Trouble Code Definitions

2007-12-10

HISTORICAL

J2012_200712

This document supersedes SAE J2012 APR2002, and is technically equivalent to ISO 15031-6:2005 with the exceptions described in Section 1.2. This document is intended to define the standardized Diagnostic Trouble Codes (DTC) that On-Board Diagnostic (OBD) systems in vehicles are required to report when malfunctions are detected. This document includes: a Diagnostic Trouble Code format. b A standardized set of Diagnostic Trouble Codes and descriptions c A standardized set of Diagnostic Trouble Codes subtypes known as Failure Types

Standard

Diagnostic Trouble Code Definitions Equivalent to ISO/DIS 15031-6:April 30, 2002

2002-04-30

HISTORICAL

J2012_200204

This SAE Recommended Practice supersedes SAE J2012 MAR1999, and is technically equivalent to ISO/DIS 15031-6:April 30, 2002. This document is intended to define the standardized Diagnostic Trouble Codes (DTC) that On-Board Diagnostic (OBD) systems in vehicles are required to report when malfunctions are detected. This document includes: a Diagnostic Trouble Code format b A standardized set of Diagnostic Trouble Codes and descriptions

Standard

RECOMMENDED PRACTICE FOR DIAGNOSTIC TROUBLE CODE DEFINITIONS

1994-10-01

HISTORICAL

J2012_199410

This SAE Recommended Practice is applicable to all light-duty and medium-duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair databases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

Standard

DIAGNOSTIC TROUBLE CODE DEFINITIONS

1992-03-01

HISTORICAL

J2012_199203

This SAE Recommended Practice is applicable to all light duty and medium duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair data bases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

Standard

RECOMMENDED PRACTICE FOR DIAGNOSTIC TROUBLE CODE DEFINITIONS

1996-07-01

HISTORICAL

J2012_199607

This SAE Recommended Practice is applicable to all light-duty and medium-duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair databases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

Standard

RECOMMENDED PRACTICE FOR DIAGNOSTIC TROUBLE CODE DEFINITIONS

1994-01-01

HISTORICAL

J2012_199401

This SAE Recommended Practice is applicable to all light-duty and medium-duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair data bases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

Standard

OBD-II Scan Tool

2022-05-26

CURRENT

J1978_202205

SAE J1978/ISO 15031-4 specifies a complementary set of functions to be provided by an OBD-II scan tool. These functions provide complete, efficient, and safe access to all regulated OBD (on-board diagnostic) services on any vehicle which is compliant with SAE J1978/ISO 15031-4. The SAE J1978 content of this document is intended to satisfy the requirements of an OBD-II scan tool as required by current U.S. on-board diagnostic (OBD) regulations. The ISO 15031-4 content of this document is intended to satisfy the requirements of OBD requirements in countries other than the U.S., and includes functionality not required or not allowed in the U.S. This document specifies: A means of establishing communications between an OBD-equipped vehicle and an OBD-II scan tool. A set of diagnostic services to be provided by an OBD-II scan tool in order to exercise the services defined in SAE J1979/ISO 15031-5.

Standard

OBD II SCAN TOOL

1998-02-01

HISTORICAL

J1978_199802

This SAE Recommended Practice defines the requirements of OBD II Scan Tools, i.e., test equipment that will interface with vehicle modules in support of the OBD II diagnostic requirements. It covers the required capabilities of and conformance criteria for OBD II Scan Tools.

Standard

OBD II SCAN TOOL

1994-06-01

HISTORICAL

J1978_199406

This SAE Recommended Practice defines the requirements of OBD II Scan Tools, i.e., test equipment that will interface with vehicle modules in support of the OBD II diagnostic requirements. It covers the required capabilities of and conformance criteria for OBD II Scan Tools.

Standard

OBD II Scan Tool — Equivalent to ISO/DIS 15031-4:December 14, 2001

2002-04-30

HISTORICAL

J1978_200204

This SAE Recommended Practice supersedes SAE J1978 FEB1998, and is technically equivalent to ISO/DIS 15031-4:December 14, 2001. This document is intended to satisfy the requirements of an OBD scan tool as required by U.S. On-Board Diagnostic (OBD) regulations. The document specifies: a A means of establishing communications between an OBD-equipped vehicle and external test equipment, b A set of diagnostic services to be provided by the external test equipment in order to exercise the services defined in SAE J1979, c Conformance criteria for the external test equipment.

Standard

OBD II SCAN TOOL

1992-03-01

HISTORICAL

J1978_199203

This SAE Recommended Practice defines the requirements of OBD II Scan Tools, i.e. test equipment that will interface with vehicle modules in support of the OBD II diagnostic requirements. It covers the required capabilities of and conformance criteria for OBD II Scan Tools.